Overview
This document guides usage of the Server Migration Tool, when the source server is WildFly 9, and the target server is JBoss EAP 7.
----------------------------------------------------------
---- JBoss Server Migration Tool -----------------------
----------------------------------------------------------
Retrieving servers...
06:08:22,972 INFO [org.wildfly.migration.core.logger] (main) SOURCE server name: WildFly Full, version: 9.0.2.Final.
06:08:22,981 INFO [org.wildfly.migration.core.logger] (main) TARGET server name: EAP, version: 7.0.0.Beta.
----------------------------------------------------------
----------------------------------------------------------
This specific server migration consists of:
Currently the migration of the host/domain controller is not yet supported.
Standalone Server Migration
The standalone server migration is just the migration of each standalone XML config file, and as a starting point, in case the tool is running in interactive mode, the user is asked if all config files should be migrated:
Server migration starting...
06:08:22,999 INFO [org.wildfly.migration.core.logger] (main) Scanning for standalone server configurations...
06:08:22,999 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/wildfly-9.0.2.Final/standalone/configuration/standalone.xml
06:08:22,999 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/wildfly-9.0.2.Final/standalone/configuration/standalone-ha.xml
06:08:22,999 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/wildfly-9.0.2.Final/standalone/configuration/standalone-full.xml
06:08:23,000 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/wildfly-9.0.2.Final/standalone/configuration/standalone-full-ha.xml
Migrate all configurations?
yes/no?
To migrate all config files the user should input y or yes, otherwise the user should input n or no, and then the tool will go through each config file, asking the user if migration of such config file should be done:
Migrate configuration /Users/emmartins/wildfly/dist/wildfly-9.0.2.Final/standalone/configuration/standalone.xml ?
yes/no?
Please note that if the tool is running in non interactive mode all config files will be migrated.
Standalone Config File Migration
The standalone config file migration consists of:
Standalone Config File Subsystems Migration
This task migrates the subsystems configuration in the source standalone server config file, which consist of:
-
Remove any unsupported subsystems
-
Migrate the configuration of deprecated legacy subsystems, into related replacements subsystems
-
Update the configuration of supported subsystems, to match defaults on JBoss EAP 7
-
Add JBoss EAP 7 new subsystems, which are included in the default JBoss EAP 7 standalone server config files
The starting of the subsystems migration is indicated by the message:
04:25:23,584 INFO [org.wildfly.migration.core.logger] (main) Migrating subsystems...
The end of the subsystems migration is indicated by the message:
04:25:24,069 INFO [org.wildfly.migration.core.logger] (main) Subsystems migration done.
batch Subsystem
The batch subsystem is not supported by JBoss EAP 7, if found its configuration will be removed from the migrated configuration file, and the console and log(s) will display the following message:
07:18:02,536 INFO [org.wildfly.migration.core.logger] (main) Unsupported subsystem batch removed.
The extension that provides the removed subsystem, if present in the configuration file, will also be removed, and in such case the console and log(s) will display the following message:
07:18:02,550 INFO [org.wildfly.migration.core.logger] (main) Unsupported extension org.wildfly.extension.batch removed.
batch-jberet Subsystem
The batch-jberet is a JBoss EAP 7 subsystem that provides support for the Java EE 7 Batch Specification, and it's default configuration is added to the migrated configuration file.
Please note that such subsystem, and related extension, is added without any interaction with the user, the migration console and log(s) will only indicate it was added, an example:
19:57:01,695 INFO [org.wildfly.migration.core.logger] (main) Extension org.wildfly.extension.batch.jberet added.
19:57:01,705 INFO [org.wildfly.migration.core.logger] (main) Subsystem batch-jberet added.
messaging Subsystem
The messaging subsystem is deprecated on JBoss EAP 7, and the tool migrates its configuration to the JBoss EAP 7 subsystem that replaces it, named Messaging ActiveMQ.
The legacy subsystem migration is done without any interaction with the user, and any issue with the legacy subsystem configuration, e.g. missing functionality, results in a warning shown in the migration console and log(s). A successful migration of the legacy subsystem configuration is indicated by the following message:
19:57:01,405 INFO [org.wildfly.migration.core.logger] (main) Subsystem messaging migrated.
Standalone Config File Security Realms Migration
JBoss EAP 7 Security Realms configuration is fully compatible with the EAP 6 Security Realms configuration, which means that no changes are required and done. As for any properties file referenced by such configuration, in case its path is not absolute then the tool will copy such file, to the path expected by the migrated config file.
The migration of Security Realms is fully automated, no user interaction is needed, and details about its execution are shown in the migration console and log(s):
12:20:53,144 INFO [org.wildfly.migration.core.logger] (main) Migrating security realms...
12:20:53,150 INFO [org.wildfly.migration.core.logger] (main) Migrating security realm: ApplicationRealm
12:20:53,153 INFO [org.wildfly.migration.core.logger] (main) Migrating security realm: ManagementRealm
12:20:53,155 INFO [org.wildfly.migration.core.logger] (main) Security realms migration done.
Standalone Config File Deployments Migration
The migration tool does not migrates deployments in the source configuration, and removes these from the migrated configuration.